Namespaces in .NET Assemblies

The QuickOPC and OPC Wizard class libraries are made up of namespaces. Each namespace contains types that you can use in your program: classes, structures, enumerations, delegates, and interfaces.

All our namespaces begin with OpcLabs name.

Although namespaces are .NET concept, with OPC Studio you will encounter them also when working from COM tools or Python, because OPC Studio builds its COM and Python support on top of the .NET assemblies.

In COM, the namespace precedes the actual type name in the objects's ProgID. In Python, namespaces are made to behave like Python module names.

OPC Studio defines types mainly in namespaces described in tables under the links below.

You can use symbols contained in the namespaces by using their fully qualified name, such as OpcLabs.EasyOpc.DataAccess.EasyDAClient. In order to save typing and achieve more readable code, you will typically instruct your compiler to make the namespaces you use often available without explicit reference. To do so:

In Visual Basic (VB.NET), place the corresponding Imports statements at the beginning of your code files.
In Visual C#, place the corresponding using directives at the beginning of your code files.
In Visual C++, place the corresponding using namespace directives at the beginning of your code files.
In Visual F#, place the corresponding open directives at the beginning of your code files.
In PowerShell, place the corresponding using namespace directives to your script files.
In Python, place the corresponding from AssemblyName import * statements in your code after importing the Python packages.

The features discussed here, or some of them, may not be available in all editions of the product. Check the QuickOPC Product Editions page for differences between the editions. The trial license has all features enabled (and is limited in period for which it provides valid data), but licenses for specific commercial editions may have functionality limitations.

Introduction

Licensing in Visual Studio